"Select Users..." button disabled in Remote Settings (Network Steve Forum)

"Select Users..." button disabled in Remote Settings

Running Windows 8 Pro with Media Center, 64-bit. This system was regular Windows 8 (64-bit) out of the box, but moved up to Pro via the Pro Pack. I can successfully access this computer via Remote Desktop using my local account, which is an adminstrator. I'd like to allow a non-administrative local user the ability to connect to the computer via Remote Desktop as well. However, I can't seem to make that work.

On other machines that were Windows 8 Pro out of the box, this is no problem. I just go to Remote Settings, click "Select Users...", choose which non-administrative users I want to allow to log in, and it works. However, on the above-referenced machine, the "Select Users..." button is disabled:

I may be wrong, but I think this is related to the fact that my computer is missing the "Remote Desktop Users" local group, among several others that should be present on Windows 8 Pro (screen shot below). Is this a bug in the process that "moves up" regular Windows 8 to Windows 8 Pro via the Pro Pack, where all of the required groups aren't added? Are there any workarounds, other than making all of the users administrators?

November 8th, 2012 2:54pm

For comparison purposes, here are the groups that I have on a machine that was Windows 8 Pro out of the box, rather than being moved up from regular Windows 8:

Proposed as answer by KarimG Wednesday, April 17, 2013 11:52 PM

Free Windows Admin Tool Kit Click here and download it now

November 8th, 2012 5:22pm

For comparison purposes, here are the groups that I have on a machine that was Windows 8 Pro out of the box, rather than being moved up from regular Windows 8:

Proposed as answer by KarimG Wednesday, April 17, 2013 11:52 PM

November 8th, 2012 5:22pm

Hi,

One of the prossible causes is the policy Allow log on thru Remote Desktop Services Properties controlled by Domain Adminstrator if this computer is a domain-joined box. Also, you need to make sure the Remote Desktop Users is listed in this policy.

Free Windows Admin Tool Kit Click here and download it now

November 12th, 2012 8:38am

I'm not sure that's the answer for my machine. I looked at this machine before and after I joined it to the domain, and the Select Users button was grayed and the Remote Desktop Users group missing in both cases.

November 19th, 2012 4:44pm

I can confirm the same holds true for a machine that just had a pro pack upgrade done on it. Anyone have any more information on this? Whether Microsoft is aware? I can't seem to find anything but this thread.

Free Windows Admin Tool Kit Click here and download it now

November 21st, 2012 8:46pm

I haven't been able to find any way to simply submit this to Microsoft as a suspected bug. Maybe there is a way, but I haven't yet figured out how. I suppose it might be that having hundreds of millions of Windows users directly sending in bug reports would be impractical. I also haven't yet found a good way to search for known bugs.

I have unmarked the proposed answer in hopes that someone else will see it and have a suggestion.

November 26th, 2012 6:57pm

Add me to the list of people who did the upgrade,...Anyways, the option to select users is also greyed out for me. I purchased an Ibuypower Windows 8 64bit machine from Newegg and then after I received it went to "add features" and purchased the propack for a total of 75.68(Including Sales Tax), which I think was a rip-off because it seems that the upgrades, including Windows Media Center can be had for much less...Ugh

Just an update...I called Microsoft Tech Support and directed the rep to this thread...He agreed that it's an issue that needs their attention and he escalated it to some higher level. Additionally he said I should be expecting a phone call tomorrow from them...

Edited by totallygreen Thursday, December 06, 2012 8:43 PM

Free Windows Admin Tool Kit Click here and download it now

December 5th, 2012 3:08am

Edited by totallygreen Thursday, December 06, 2012 8:43 PM

December 5th, 2012 3:08am

I haven't been able to find any way to simply submit this to Microsoft as a suspected bug. Maybe there is a way, but I haven't yet figured out how. I suppose it might be that having hundreds of millions of Windows users directly sending in bug reports would be impractical. I also haven't yet found a good way to search for known bugs.

I have unmarked the proposed answer in hopes that someone else will see it and have a suggestion.

Hi jesman,

could you share the files under "C:\windows\logs\CBS\", and what is your email address, may be we can save some communication cost.

Free Windows Admin Tool Kit Click here and download it now

December 12th, 2012 2:09am

Add me to the list of people who did the upgrade,...Anyways, the option to select users is also greyed out for me. I purchased an Ibuypower Windows 8 64bit machine from Newegg and then after I received it went to "add features" and purchased the propack for a total of 75.68(Including Sales Tax), which I think was a rip-off because it seems that the upgrades, including Windows Media Center can be had for much less...Ugh

Just an update...I called Microsoft Tech Support and directed the rep to this thread...He agreed that it's an issue that needs their attention and he escalated it to some higher level. Additionally he said I should be expecting a phone call tomorrow from them...

hi , did the Tech Support team have any conclution ?

December 12th, 2012 2:11am

Add me to the list of people who did the upgrade,...Anyways, the option to select users is also greyed out for me. I purchased an Ibuypower Windows 8 64bit machine from Newegg and then after I received it went to "add features" and purchased the propack for a total of 75.68(Including Sales Tax), which I think was a rip-off because it seems that the upgrades, including Windows Media Center can be had for much less...Ugh

Just an update...I called Microsoft Tech Support and directed the rep to this thread...He agreed that it's an issue that needs their attention and he escalated it to some higher level. Additionally he said I should be expecting a phone call tomorrow from them...

hi , did the Tech Support team have any conclution ?

NO...I'm still going thru the process...They elevated my support request to the "Development" team and the next day I received a phone call from the development team...The wanted access to my computer. Unfortunately I was at work and couldn't give them access. I asked them to call me back in the evening when I was home and so far they have not called me back...:( That was two days ago.

Earlier today I did receive a phone call from the basic rep...I explained the problem, told them they can easily reproduce the issue and they don't need to access my machine...However in the interests of getting resolution, please have the development team call me in the evening...I'm still waiting for the phone call.

I plan on installing the free logmein so if they call when I'm at work, I can at least try and get them onto my machine...who knows if that will work though because I think they also use the same logmein technology when accessing customer's machines and the two working together will probably be an issue...

Free Windows Admin Tool Kit Click here and download it now

December 12th, 2012 11:18pm

Add me to the list of people who did the upgrade,...Anyways, the option to select users is also greyed out for me. I purchased an Ibuypower Windows 8 64bit machine from Newegg and then after I received it went to "add features" and purchased the propack for a total of 75.68(Including Sales Tax), which I think was a rip-off because it seems that the upgrades, including Windows Media Center can be had for much less...Ugh

Just an update...I called Microsoft Tech Support and directed the rep to this thread...He agreed that it's an issue that needs their attention and he escalated it to some higher level. Additionally he said I should be expecting a phone call tomorrow from them...

hi , did the Tech Support team have any conclution ?

NO...I'm still going thru the process...They elevated my support request to the "Development" team and the next day I received a phone call from the development team...The wanted access to my computer. Unfortunately I was at work and couldn't give them access. I asked them to call me back in the evening when I was home and so far they have not called me back...:( That was two days ago.

Earlier today I did receive a phone call from the basic rep...I explained the problem, told them they can easily reproduce the issue and they don't need to access my machine...However in the interests of getting resolution, please have the development team call me in the evening...I'm still waiting for the phone call.

I plan on installing the free logmein so if they call when I'm at work, I can at least try and get them onto my machine...who knows if that will work though because I think they also use the same logmein technology when accessing customer's machines and the two working together will probably be an issue...

I'm not related to them, but could you share the logs under "C:\windows\logs\CBS\"? it's the log of windows upgrade. Thanks

December 13th, 2012 1:35am

You can reach me at the following email address: jesman at outlook dot com.

I'm looking at the log files in the CBS folder. Here's a link to the oldest one, which has dates 11/13 - 11/29 (compressed as a CAB file):

https://skydrive.live.com/redir?resid=44D346876078177A!203&authkey=!AON4tw8yzBCBvCw

Free Windows Admin Tool Kit Click here and download it now

December 13th, 2012 1:52am

You can reach me at the following email address: jesman at outlook dot com.

I'm looking at the log files in the CBS folder. Here's a link to the oldest one, which has dates 11/13 - 11/29 (compressed as a CAB file):

https://skydrive.live.com/redir?resid=44D346876078177A!203&authkey=!AON4tw8yzBCBvCw

Thanks for your quick response. I will let you know if we have any result. Thanks.

December 13th, 2012 2:52am

I seem to have the same problem with a Win8 32-bit install that was upgraded with Pro Pack. The "Select Users" button in Remote Settings is grayed and the Local Users and Groups are missing, identically to the OP screen shot.

Free Windows Admin Tool Kit Click here and download it now

December 18th, 2012 1:28pm

Same exact problem here. I just got off my *second* 1.5 hour Microsoft tech phone call/remote assistance. At the end of the day, they said that I needed to port forward from 3389 and use my current IP address to look for the computer from my client laptop. I'm unfortunately out of state at the moment so am unable to forward the port and try it (though I know my current IP of the host computer because I'm using the free LogMeIn software). I barely got the tech to admit there was anything out of the ordinary for this kind of issues to exist. He said he hadn't dealt with this because "not many people use Remote Desktop."

December 19th, 2012 10:42pm

Same exact problem here. I just got off my *second* 1.5 hour Microsoft tech phone call/remote assistance. At the end of the day, they said that I needed to port forward from 3389 and use my current IP address to look for the computer from my client laptop. I'm unfortunately out of state at the moment so am unable to forward the port and try it (though I know my current IP of the host computer because I'm using the free LogMeIn software). I barely got the tech to admit there was anything out of the ordinary for this kind of issues to exist. He said he hadn't dealt with this because "not many people use Remote Desktop."

Thanks for the update and thanks for calling...Unfortunately, I think that because it doesn't effect anyone who matters at Microsoft(Because they did not upgrade to pro via the pro pack) , there probably is not any fix in the near future. I gave up on Tech Support after they never called me back in the evening...I'm thinking of asking for a refund.

Huge thanks to QingFUW for looking into this, if you still want my logs, I'll gladly send them...Thanks again.

The main reason I upgraded was for remote desktop and it just doesn't work, even when I try to connect from within my home network(So it's not a port forwarding issue). I see the OP was able to connect using a local account, but my logon is linked to my Microsoft account and it just doesn't work.

Free Windows Admin Tool Kit Click here and download it now

December 19th, 2012 11:10pm

Same exact problem here. I just got off my *second* 1.5 hour Microsoft tech phone call/remote assistance. At the end of the day, they said that I needed to port forward from 3389 and use my current IP address to look for the computer from my client laptop. I'm unfortunately out of state at the moment so am unable to forward the port and try it (though I know my current IP of the host computer because I'm using the free LogMeIn software). I barely got the tech to admit there was anything out of the ordinary for this kind of issues to exist. He said he hadn't dealt with this because "not many people use Remote Desktop."

Thanks for the update and thanks for calling...Unfortunately, I think that because it doesn't effect anyone who matters at Microsoft(Because they did not upgrade to pro via the pro pack) , there probably is not any fix in the near future. I gave up on Tech Support after they never called me back in the evening...I'm thinking of asking for a refund.

Huge thanks to QingFUW for looking into this, if you still want my logs, I'll gladly send them...Thanks again.

The main reason I upgraded was for remote desktop and it just doesn't work, even when I try to connect from within my home network(So it's not a port forwarding issue). I see the OP was able to connect using a local account, but my logon is linked to my Microsoft account and it just doesn't work.

Just let you know My email thread about this issue is not closed yet. I'm still waiting for someone's reply.

December 21st, 2012 2:48am

Same exact problem here. I just got off my *second* 1.5 hour Microsoft tech phone call/remote assistance. At the end of the day, they said that I needed to port forward from 3389 and use my current IP address to look for the computer from my client laptop. I'm unfortunately out of state at the moment so am unable to forward the port and try it (though I know my current IP of the host computer because I'm using the free LogMeIn software). I barely got the tech to admit there was anything out of the ordinary for this kind of issues to exist. He said he hadn't dealt with this because "not many people use Remote Desktop."

I have port forwarding set up on the router and I've found that I can RDP into the machine both locally and from the internet, when logging in as administrator. The problem comes when trying to log in as another user. Because the "select users" button is grayed, I get an error when trying to RDP in using non-admin credentials.

Free Windows Admin Tool Kit Click here and download it now

January 2nd, 2013 4:20am

Just let you know My email thread about this issue is not closed yet. I'm still waiting for someone's reply.

Thanks for following this up QingFUW. If the upgrade logs for a 32-bit Windows 8 install will help, please let me know.

January 2nd, 2013 4:23am

I am facing the same issue. Need Help.

Free Windows Admin Tool Kit Click here and download it now

January 7th, 2013 6:33pm

Having same problem. I have a client that bought a bunch of new computers that had to be upgraded and his staff logs in remotely.

January 8th, 2013 3:31pm

Same Problem here, upgraded from plain Win8 to Win8Pro. Does not allow me to select users in Remote Desktop Connection settings.... No RDP connection possible for non Admin users...

Very BAD !

Free Windows Admin Tool Kit Click here and download it now

January 9th, 2013 10:42am

I have definitely confirmed this exact issue on two machines where I moved up to the Pro Pak. I have not contacted MS directly but I'm hoping to follow this thread and wait for resolution. We are only a 100+ network but I do not plan to upgrade any more employee computers until this has been resolved. RDP is our primary option for connecting remotely. This seems like a pretty bad bug/issue in my opinion. Hopefully easily fixed through a WSUS update though.

January 9th, 2013 7:39pm

Guys,

I figured it out, well, partially. After upgrading to Windows 8 Pro via the Pro Pack, I ran into the same issue. As many of you have stated, the Remote Desktop Users group is missing. This is obviously a bug and a group that's needed for services like TightVNC to connect.

All I did was to create a group called Remote Desktop Users and add our Domain Admins group to it. After a restart, I was able to remote into the Windows 8 machine that just had Pro Pack installed.

Hope this helps!

Edited by Nate1630 Thursday, January 17, 2013 3:04 PM

Free Windows Admin Tool Kit Click here and download it now

January 17th, 2013 3:04pm

Guys,

All I did was to create a group called Remote Desktop Users and add our Domain Admins group to it. After a restart, I was able to remote into the Windows 8 machine that just had Pro Pack installed.

Hope this helps!

Edited by Nate1630 Thursday, January 17, 2013 3:04 PM

January 17th, 2013 3:04pm

Guys,

I figured it out, well, partially. After upgrading to Windows 8 Pro via the Pro Pack, I ran into the same issue. As many of you have stated, the Remote Desktop Users group is missing. This is obviously a bug and a group that's needed for services like TightVNC to connect.

All I did was to create a group called Remote Desktop Users and add our Domain Admins group to it. After a restart, I was able to remote into the Windows 8 machine that just had Pro Pack installed.

Hope this helps!

Domain Admins always have Remote Desktop Access provided the service is enabled this is NOT in fact a solution because it does not enable the ability to select non administrative users and grant them remote desktop access.

I have two systems that were upgraded to Windows 8 Pro from standard Windows 8 and both are experiencing this issue.

One work around that is in no way ideal is to add your non Domain Admin users to the Administrators group of the local system, this will give them admin rights to the specific system and will let the Remote Desktop into the PC. I personally don't find this to be an acceptable resolution and will be reaching out to Microsoft to find out what can be done.

I'll post a solution if I find one.

Edited by Ylindsay Tuesday, January 22, 2013 3:09 PM Edited for clarification

Free Windows Admin Tool Kit Click here and download it now

January 22nd, 2013 3:01pm

Guys,

I figured it out, well, partially. After upgrading to Windows 8 Pro via the Pro Pack, I ran into the same issue. As many of you have stated, the Remote Desktop Users group is missing. This is obviously a bug and a group that's needed for services like TightVNC to connect.

All I did was to create a group called Remote Desktop Users and add our Domain Admins group to it. After a restart, I was able to remote into the Windows 8 machine that just had Pro Pack installed.

Hope this helps!

I have two systems that were upgraded to Windows 8 Pro from standard Windows 8 and both are experiencing this issue.

I'll post a solution if I find one.

Edited by Ylindsay Tuesday, January 22, 2013 3:09 PM Edited for clarification

January 22nd, 2013 3:01pm

Exactly the same problem. Particularly annoying since the primary reason why I purchased Windows 8 Pro Pack was so that it would be possible for all users (including those with local accounts and non-administrator rights) to connect remotely. And now it doesn't work. It doesn't look as though anybody has come up with a satisfactory solution/workaround yet (giving all users administrator rights is most certainly not satisfactory).

Edited by MrWinnieThePooh Monday, February 04, 2013 9:21 AM

Free Windows Admin Tool Kit Click here and download it now

February 4th, 2013 9:18am

Edited by MrWinnieThePooh Monday, February 04, 2013 9:21 AM

February 4th, 2013 9:18am

Does anyone have a solution to this yet? Have just been chatting to MS Live Support and the guy recommended I use the "Refresh Windows 8 " or "Reset Windows 8" functions which apparently reset the user groups. I don't want to go through the hassle of this, plus reinstalling/configuring my apps if someone has already tried this (and failed!) or has an alternative solution.

Thanks!

Hoss

Free Windows Admin Tool Kit Click here and download it now

February 15th, 2013 8:36pm

I have the same problem. I just ran "Refresh Windows 8" and the missing user groups have been rebuilt, although it popped up "Errors installing Windows 8" while "refreshing".

February 19th, 2013 5:05am

I've had a ticket open with Microsoft since i made my last post.

Thus far the only 'troubleshooting' responses I have recieved from them have been links back to this exact forum!

Again if Microsoft does provide an answer I will be sure to relay it here.

Free Windows Admin Tool Kit Click here and download it now

March 1st, 2013 9:39pm

Following S.Law's suggestion, I did the following: If you save all your data (just in case), find all your App installers (and Keys/PIDs), then go to Settings, PC Settings, General. There you will find "Refresh your PC without affecting your files" Run it.

It will take a while, and after close to an hour (maybe less on faster PCs) it will tell you that it failed and nothing was changed. However, if you check the Groups now and Check the Remote Settings tab in System Properties, you'll find that it's fixed. I realize it's counterintuitive, but it WORKED for me. You will have to reinstall all your apps though. . . .

Proposed as answer by Bluechips10 Friday, March 08, 2013 7:27 PM

March 8th, 2013 7:27pm

Proposed as answer by Bluechips10 Friday, March 08, 2013 7:27 PM

Free Windows Admin Tool Kit Click here and download it now

March 8th, 2013 7:27pm

Why can't you just recreate the group manually and assign it the ability to use Remote Desktop login via local security policy?

That seems a better solution than blowing away your applications.

March 8th, 2013 8:47pm

Here is a different post ( from someone named adhodgson1) I found that address that [MG42's] question:

"Hi,

I have the same problem for some users who I purchased pro packs for, and in fact wanted to connect them to the Windows |Server Essentials 2012 system. The setup of the WSE 2012 software fails because it can't find the Remote Desktop Users group. Re-creating that group doesn't work either because the software looks for the group SID. MS need to investigate the issue and post a fix, because there are several other threads on the forums regarding this issue.

Thanks.
Andrew."

Bluechips10

Free Windows Admin Tool Kit Click here and download it now

March 9th, 2013 4:14pm

I have also experienced this issue.

I have contacted Microsoft. So far they have refused to case a support incident. After some arguing they have confirmed the issue is currently being investigating by the Microsoft Global Escalation team, but there is no ETA for resolution.

I tried a full retail Windows 8 Pro key as an upgrade (i.e. using Add Features -> I already have a product key) and the problem does not occur, which shows the issue is linked to the Pro Pack keys only. On this basis I told Microsoft that the Pro Packs are faulty, and requested they supply me with a working product key, however so far no response. So I came up with my own solution

1)
If you already created the groups manually in Local Users and Groups delete them, as they wont have the correct SIDs like the Builtin groups should.

2)
Launch regedit with Administrator rights, navigate to HKLM\SAM\SAM, right click on the key and select Permissions (be sure to go to SAM\SAM, not just SAM). Add your current admin user to the list and give Full Control. If your permissions are correctly applied, press F5 and then you should be able to access additional sub-keys.

3)
Go to File -> Import and import my .reg file (see below to create the file)
This will create the 8 missing groups.
This information was exported from a clean build of Windows 8 Pro (not an upgrade), so the groups should have the correct SIDs.

4)
Repeat step 2 but this time remove your user account from HKLM\SAM\SAM permissions, to restore original permissions.
Restart.

The missing groups are now showing in Local Users and Groups and they are also referenced correctly in the local security policies user rights assignment.

What I do not know is:
- What else could be missed caused by the Pro Pack upgrade routine?
- Are there missing references to the groups somewhere else in Windows?

So I cannot guarantee what future implications there might be, but at least this did solve the immediate issue.

It would be nice if Microsoft could publically acknowledge this issue and provide a Fix-It tool to automate the above and fill in any other gaps that may exist!

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\00000243] "C"=hex:43,02,00,00,00,00,00,00,b0,00,00,00,02,00,01,00,b0,00,00,00,46,00,00,\ 00,00,00,00,00,f8,00,00,00,e2,00,00,00,00,00,00,00,dc,01,00,00,00,00,00,00,\ 00,00,00,00,01,00,14,80,90,00,00,00,a0,00,00,00,14,00,00,00,44,00,00,00,02,\ 00,30,00,02,00,00,00,02,c0,14,00,13,00,05,01,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,c0,14,00,ff,ff,1f,00,01,01,00,00,00,00,00,05,07,00,00,00,02,00,4c,\ 00,03,00,00,00,00,00,14,00,0c,00,02,00,01,01,00,00,00,00,00,01,00,00,00,00,\ 00,00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\ 00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,24,02,00,00,01,02,\ 00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,00,\ 00,20,02,00,00,41,00,63,00,63,00,65,00,73,00,73,00,20,00,43,00,6f,00,6e,00,\ 74,00,72,00,6f,00,6c,00,20,00,41,00,73,00,73,00,69,00,73,00,74,00,61,00,6e,\ 00,63,00,65,00,20,00,4f,00,70,00,65,00,72,00,61,00,74,00,6f,00,72,00,73,00,\ 00,00,4d,00,65,00,6d,00,62,00,65,00,72,00,73,00,20,00,6f,00,66,00,20,00,74,\ 00,68,00,69,00,73,00,20,00,67,00,72,00,6f,00,75,00,70,00,20,00,63,00,61,00,\ 6e,00,20,00,72,00,65,00,6d,00,6f,00,74,00,65,00,6c,00,79,00,20,00,71,00,75,\ 00,65,00,72,00,79,00,20,00,61,00,75,00,74,00,68,00,6f,00,72,00,69,00,7a,00,\ 61,00,74,00,69,00,6f,00,6e,00,20,00,61,00,74,00,74,00,72,00,69,00,62,00,75,\ 00,74,00,65,00,73,00,20,00,61,00,6e,00,64,00,20,00,70,00,65,00,72,00,6d,00,\ 69,00,73,00,73,00,69,00,6f,00,6e,00,73,00,20,00,66,00,6f,00,72,00,20,00,72,\ 00,65,00,73,00,6f,00,75,00,72,00,63,00,65,00,73,00,20,00,6f,00,6e,00,20,00,\ 74,00,68,00,69,00,73,00,20,00,63,00,6f,00,6d,00,70,00,75,00,74,00,65,00,72,\ 00,2e,00,00,00 [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\00000227] "C"=hex:27,02,00,00,00,00,00,00,b0,00,00,00,02,00,01,00,b0,00,00,00,20,00,00,\ 00,00,00,00,00,d0,00,00,00,d2,00,00,00,00,00,00,00,a4,01,00,00,00,00,00,00,\ 00,00,00,00,01,00,14,80,90,00,00,00,a0,00,00,00,14,00,00,00,44,00,00,00,02,\ 00,30,00,02,00,00,00,02,c0,14,00,13,00,05,01,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,c0,14,00,ff,ff,1f,00,01,01,00,00,00,00,00,05,07,00,00,00,02,00,4c,\ 00,03,00,00,00,00,00,14,00,0c,00,02,00,01,01,00,00,00,00,00,01,00,00,00,00,\ 00,00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\ 00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,24,02,00,00,01,02,\ 00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,00,\ 00,20,02,00,00,42,00,61,00,63,00,6b,00,75,00,70,00,20,00,4f,00,70,00,65,00,\ 72,00,61,00,74,00,6f,00,72,00,73,00,42,00,61,00,63,00,6b,00,75,00,70,00,20,\ 00,4f,00,70,00,65,00,72,00,61,00,74,00,6f,00,72,00,73,00,20,00,63,00,61,00,\ 6e,00,20,00,6f,00,76,00,65,00,72,00,72,00,69,00,64,00,65,00,20,00,73,00,65,\ 00,63,00,75,00,72,00,69,00,74,00,79,00,20,00,72,00,65,00,73,00,74,00,72,00,\ 69,00,63,00,74,00,69,00,6f,00,6e,00,73,00,20,00,66,00,6f,00,72,00,20,00,74,\ 00,68,00,65,00,20,00,73,00,6f,00,6c,00,65,00,20,00,70,00,75,00,72,00,70,00,\ 6f,00,73,00,65,00,20,00,6f,00,66,00,20,00,62,00,61,00,63,00,6b,00,69,00,6e,\ 00,67,00,20,00,75,00,70,00,20,00,6f,00,72,00,20,00,72,00,65,00,73,00,74,00,\ 6f,00,72,00,69,00,6e,00,67,00,20,00,66,00,69,00,6c,00,65,00,73,00,00,00 [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\00000239] "C"=hex:39,02,00,00,00,00,00,00,b0,00,00,00,02,00,01,00,b0,00,00,00,2e,00,00,\ 00,00,00,00,00,e0,00,00,00,76,00,00,00,00,00,00,00,58,01,00,00,00,00,00,00,\ 00,00,00,00,01,00,14,80,90,00,00,00,a0,00,00,00,14,00,00,00,44,00,00,00,02,\ 00,30,00,02,00,00,00,02,c0,14,00,13,00,05,01,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,c0,14,00,ff,ff,1f,00,01,01,00,00,00,00,00,05,07,00,00,00,02,00,4c,\ 00,03,00,00,00,00,00,14,00,0c,00,02,00,01,01,00,00,00,00,00,01,00,00,00,00,\ 00,00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\ 00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,24,02,00,00,01,02,\ 00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,00,\ 00,20,02,00,00,43,00,72,00,79,00,70,00,74,00,6f,00,67,00,72,00,61,00,70,00,\ 68,00,69,00,63,00,20,00,4f,00,70,00,65,00,72,00,61,00,74,00,6f,00,72,00,73,\ 00,00,00,4d,00,65,00,6d,00,62,00,65,00,72,00,73,00,20,00,61,00,72,00,65,00,\ 20,00,61,00,75,00,74,00,68,00,6f,00,72,00,69,00,7a,00,65,00,64,00,20,00,74,\ 00,6f,00,20,00,70,00,65,00,72,00,66,00,6f,00,72,00,6d,00,20,00,63,00,72,00,\ 79,00,70,00,74,00,6f,00,67,00,72,00,61,00,70,00,68,00,69,00,63,00,20,00,6f,\ 00,70,00,65,00,72,00,61,00,74,00,69,00,6f,00,6e,00,73,00,2e,00,00,00 [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\00000242] "C"=hex:42,02,00,00,00,00,00,00,b0,00,00,00,02,00,01,00,b0,00,00,00,2c,00,00,\ 00,00,00,00,00,dc,00,00,00,ae,00,00,00,00,00,00,00,8c,01,00,00,00,00,00,00,\ 00,00,00,00,01,00,14,80,90,00,00,00,a0,00,00,00,14,00,00,00,44,00,00,00,02,\ 00,30,00,02,00,00,00,02,c0,14,00,13,00,05,01,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,c0,14,00,ff,ff,1f,00,01,01,00,00,00,00,00,05,07,00,00,00,02,00,4c,\ 00,03,00,00,00,00,00,14,00,0c,00,02,00,01,01,00,00,00,00,00,01,00,00,00,00,\ 00,00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\ 00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,24,02,00,00,01,02,\ 00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,00,\ 00,20,02,00,00,48,00,79,00,70,00,65,00,72,00,2d,00,56,00,20,00,41,00,64,00,\ 6d,00,69,00,6e,00,69,00,73,00,74,00,72,00,61,00,74,00,6f,00,72,00,73,00,4d,\ 00,65,00,6d,00,62,00,65,00,72,00,73,00,20,00,6f,00,66,00,20,00,74,00,68,00,\ 69,00,73,00,20,00,67,00,72,00,6f,00,75,00,70,00,20,00,68,00,61,00,76,00,65,\ 00,20,00,63,00,6f,00,6d,00,70,00,6c,00,65,00,74,00,65,00,20,00,61,00,6e,00,\ 64,00,20,00,75,00,6e,00,72,00,65,00,73,00,74,00,72,00,69,00,63,00,74,00,65,\ 00,64,00,20,00,61,00,63,00,63,00,65,00,73,00,73,00,20,00,74,00,6f,00,20,00,\ 61,00,6c,00,6c,00,20,00,66,00,65,00,61,00,74,00,75,00,72,00,65,00,73,00,20,\ 00,6f,00,66,00,20,00,48,00,79,00,70,00,65,00,72,00,2d,00,56,00,2e,00,00,00 [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\0000022C] "C"=hex:2c,02,00,00,00,00,00,00,b0,00,00,00,02,00,01,00,b0,00,00,00,3e,00,00,\ 00,00,00,00,00,f0,00,00,00,d8,00,00,00,00,00,00,00,c8,01,00,00,00,00,00,00,\ 00,00,00,00,01,00,14,80,90,00,00,00,a0,00,00,00,14,00,00,00,44,00,00,00,02,\ 00,30,00,02,00,00,00,02,c0,14,00,13,00,05,01,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,c0,14,00,ff,ff,1f,00,01,01,00,00,00,00,00,05,07,00,00,00,02,00,4c,\ 00,03,00,00,00,00,00,14,00,0c,00,02,00,01,01,00,00,00,00,00,01,00,00,00,00,\ 00,00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\ 00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,24,02,00,00,01,02,\ 00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,00,\ 00,20,02,00,00,4e,00,65,00,74,00,77,00,6f,00,72,00,6b,00,20,00,43,00,6f,00,\ 6e,00,66,00,69,00,67,00,75,00,72,00,61,00,74,00,69,00,6f,00,6e,00,20,00,4f,\ 00,70,00,65,00,72,00,61,00,74,00,6f,00,72,00,73,00,00,00,4d,00,65,00,6d,00,\ 62,00,65,00,72,00,73,00,20,00,69,00,6e,00,20,00,74,00,68,00,69,00,73,00,20,\ 00,67,00,72,00,6f,00,75,00,70,00,20,00,63,00,61,00,6e,00,20,00,68,00,61,00,\ 76,00,65,00,20,00,73,00,6f,00,6d,00,65,00,20,00,61,00,64,00,6d,00,69,00,6e,\ 00,69,00,73,00,74,00,72,00,61,00,74,00,69,00,76,00,65,00,20,00,70,00,72,00,\ 69,00,76,00,69,00,6c,00,65,00,67,00,65,00,73,00,20,00,74,00,6f,00,20,00,6d,\ 00,61,00,6e,00,61,00,67,00,65,00,20,00,63,00,6f,00,6e,00,66,00,69,00,67,00,\ 75,00,72,00,61,00,74,00,69,00,6f,00,6e,00,20,00,6f,00,66,00,20,00,6e,00,65,\ 00,74,00,77,00,6f,00,72,00,6b,00,69,00,6e,00,67,00,20,00,66,00,65,00,61,00,\ 74,00,75,00,72,00,65,00,73,00 [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\00000223] "C"=hex:23,02,00,00,00,00,00,00,b0,00,00,00,02,00,01,00,b0,00,00,00,16,00,00,\ 00,00,00,00,00,c8,00,00,00,bc,00,00,00,00,00,00,00,84,01,00,00,00,00,00,00,\ 00,00,00,00,01,00,14,80,90,00,00,00,a0,00,00,00,14,00,00,00,44,00,00,00,02,\ 00,30,00,02,00,00,00,02,c0,14,00,13,00,05,01,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,c0,14,00,ff,ff,1f,00,01,01,00,00,00,00,00,05,07,00,00,00,02,00,4c,\ 00,03,00,00,00,00,00,14,00,0c,00,02,00,01,01,00,00,00,00,00,01,00,00,00,00,\ 00,00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\ 00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,24,02,00,00,01,02,\ 00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,00,\ 00,20,02,00,00,50,00,6f,00,77,00,65,00,72,00,20,00,55,00,73,00,65,00,72,00,\ 73,00,00,00,50,00,6f,00,77,00,65,00,72,00,20,00,55,00,73,00,65,00,72,00,73,\ 00,20,00,61,00,72,00,65,00,20,00,69,00,6e,00,63,00,6c,00,75,00,64,00,65,00,\ 64,00,20,00,66,00,6f,00,72,00,20,00,62,00,61,00,63,00,6b,00,77,00,61,00,72,\ 00,64,00,73,00,20,00,63,00,6f,00,6d,00,70,00,61,00,74,00,69,00,62,00,69,00,\ 6c,00,69,00,74,00,79,00,20,00,61,00,6e,00,64,00,20,00,70,00,6f,00,73,00,73,\ 00,65,00,73,00,73,00,20,00,6c,00,69,00,6d,00,69,00,74,00,65,00,64,00,20,00,\ 61,00,64,00,6d,00,69,00,6e,00,69,00,73,00,74,00,72,00,61,00,74,00,69,00,76,\ 00,65,00,20,00,70,00,6f,00,77,00,65,00,72,00,73,00 [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\0000022B]
"C"=hex:2b,02,00,00,00,00,00,00,b0,00,00,00,02,00,01,00,b0,00,00,00,28,00,00,\
00,00,00,00,00,d8,00,00,00,7a,00,00,00,00,00,00,00,54,01,00,00,00,00,00,00,\
00,00,00,00,01,00,14,80,90,00,00,00,a0,00,00,00,14,00,00,00,44,00,00,00,02,\
00,30,00,02,00,00,00,02,c0,14,00,13,00,05,01,01,01,00,00,00,00,00,01,00,00,\
00,00,02,c0,14,00,ff,ff,1f,00,01,01,00,00,00,00,00,05,07,00,00,00,02,00,4c,\
00,03,00,00,00,00,00,14,00,0c,00,02,00,01,01,00,00,00,00,00,01,00,00,00,00,\
00,00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\
00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,24,02,00,00,01,02,\
00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,00,\
00,20,02,00,00,52,00,65,00,6d,00,6f,00,74,00,65,00,20,00,44,00,65,00,73,00,\
6b,00,74,00,6f,00,70,00,20,00,55,00,73,00,65,00,72,00,73,00,4d,00,65,00,6d,\
00,62,00,65,00,72,00,73,00,20,00,69,00,6e,00,20,00,74,00,68,00,69,00,73,00,\
20,00,67,00,72,00,6f,00,75,00,70,00,20,00,61,00,72,00,65,00,20,00,67,00,72,\
00,61,00,6e,00,74,00,65,00,64,00,20,00,74,00,68,00,65,00,20,00,72,00,69,00,\
67,00,68,00,74,00,20,00,74,00,6f,00,20,00,6c,00,6f,00,67,00,6f,00,6e,00,20,\
00,72,00,65,00,6d,00,6f,00,74,00,65,00,6c,00,79,00,00,00
[HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\00000228] "C"=hex:28,02,00,00,00,00,00,00,b0,00,00,00,02,00,01,00,b0,00,00,00,14,00,00,\ 00,00,00,00,00,c4,00,00,00,4a,00,00,00,00,00,00,00,10,01,00,00,00,00,00,00,\ 00,00,00,00,01,00,14,80,90,00,00,00,a0,00,00,00,14,00,00,00,44,00,00,00,02,\ 00,30,00,02,00,00,00,02,c0,14,00,13,00,05,01,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,c0,14,00,ff,ff,1f,00,01,01,00,00,00,00,00,05,07,00,00,00,02,00,4c,\ 00,03,00,00,00,00,00,14,00,0c,00,02,00,01,01,00,00,00,00,00,01,00,00,00,00,\ 00,00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\ 00,18,00,1f,00,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,24,02,00,00,01,02,\ 00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,00,\ 00,20,02,00,00,52,00,65,00,70,00,6c,00,69,00,63,00,61,00,74,00,6f,00,72,00,\ 53,00,75,00,70,00,70,00,6f,00,72,00,74,00,73,00,20,00,66,00,69,00,6c,00,65,\ 00,20,00,72,00,65,00,70,00,6c,00,69,00,63,00,61,00,74,00,69,00,6f,00,6e,00,\ 20,00,69,00,6e,00,20,00,61,00,20,00,64,00,6f,00,6d,00,61,00,69,00,6e,00,00,\ 00 [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\Names\Access Control Assistance Operators] @=hex(243): [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\Names\Backup Operators] @=hex(227): [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\Names\Cryptographic Operators] @=hex(239): [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\Names\Hyper-V Administrators] @=hex(242): [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\Names\Network Configuration Operators] @=hex(22c): [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\Names\Power Users] @=hex(223): [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\Names\Remote Desktop Users] @=hex(22b): [HKEY_LOCAL_MACHINE\SAM\SAM\Domains\Builtin\Aliases\Names\Replicator] @=hex(228):

Edited by i74 Wednesday, March 27, 2013 5:57 AM
Proposed as answer by Peter Swarowski Thursday, April 04, 2013 11:09 PM

March 27th, 2013 4:28am

I have also experienced this issue.

1)
If you already created the groups manually in Local Users and Groups delete them, as they wont have the correct SIDs like the Builtin groups should.

4)
Repeat step 2 but this time remove your user account from HKLM\SAM\SAM permissions, to restore original permissions.
Restart.

The missing groups are now showing in Local Users and Groups and they are also referenced correctly in the local security policies user rights assignment.

What I do not know is:
- What else could be missed caused by the Pro Pack upgrade routine?
- Are there missing references to the groups somewhere else in Windows?

So I cannot guarantee what future implications there might be, but at least this did solve the immediate issue.

It would be nice if Microsoft could publically acknowledge this issue and provide a Fix-It tool to automate the above and fill in any other gaps that may exist!

Edited by i74 Wednesday, March 27, 2013 5:57 AM
Proposed as answer by Peter Swarowski Thursday, April 04, 2013 11:09 PM

Free Windows Admin Tool Kit Click here and download it now

March 27th, 2013 4:28am

I would like to add myself to the growing number of people having problems with WIN8 PRO Upgrade and not being able to add Non-Admin users to Remote Desktop. Like other posters here I can Remote Desktop with my domain admin user account but have no option to add other users to the list like in WIN XP, Vista and WIN7 workstations. Please get this fixed!!

April 4th, 2013 2:30am

I have also experienced this issue.

1)
If you already created the groups manually in Local Users and Groups delete them, as they wont have the correct SIDs like the Builtin groups should.

4)
Repeat step 2 but this time remove your user account from HKLM\SAM\SAM permissions, to restore original permissions.
Restart.

The missing groups are now showing in Local Users and Groups and they are also referenced correctly in the local security policies user rights assignment.

What I do not know is:
- What else could be missed caused by the Pro Pack upgrade routine?
- Are there missing references to the groups somewhere else in Windows?

So I cannot guarantee what future implications there might be, but at least this did solve the immediate issue.

It would be nice if Microsoft could publically acknowledge this issue and provide a Fix-It tool to automate the above and fill in any other gaps that may exist!

This worked for me

Free Windows Admin Tool Kit Click here and download it now

April 4th, 2013 11:09pm

I have also experienced this issue.

I have contacted Microsoft. So far they have refused to case a support incident. After some arguing they have confirmed the issue is currently being investigating by the Microsoft Global Escalation team, but there is no ETA for resolution.

I tried a full retail Windows 8 Pro key as an upgrade (i.e. using Add Features -> I already have a product key) and the problem does not occur, which shows the issue is linked to the Pro Pack keys only. On this basis I told Microsoft that the Pro Packs are faulty, and requested they supply me with a working product key, however so far no response. So I came up with my own solution

.....
This worked for me

Yes, i74's suggestion from 27th March worked fine for me, too. Quick and easy. Very pleased - this problem had been an ongoing annoyance. Of course, I would have preferred to have had a fix from Microsoft, rather than downloading a registry edit from a web-site, but I was prepared to take the risk. Let's hope there are no side effects.

April 14th, 2013 11:00am

I cannot get the registry file to import. I get this error: "Cannot import C:\my.reg: Error accessing the registry." I have verified that I change the permissions for the correct SAM folder. I also have tried this logging in as a local administrator account and a domain administrator account. Any ideas?

Free Windows Admin Tool Kit Click here and download it now

April 15th, 2013 8:36pm

Hey guys, I am not sure why MS is playing dumb on this one but this is not a bug that needs a fix it. Since the beginning of Media Center, Remote Desktop was only for Admin purposes. Not only that, but the first versions of Windows Media Center would not even allow to register the PC onto a domain. The issue is that they combined the PRO version with the Media Center in their pack upgrade. They should give a choice of upgrading to PRO only, or PRO with Media Center. Actually the Media Center was supposed to be gone on Windows 8, but they kept it because of all the demands.

It basically comes down to reinstalling with a Windows 8 PRO from scratch and not use their PRO pack. It is all a licensing scheme which is really bad. Windows 8 is an awesome evolution that is changing the world of computing. They really do not need to play dumb, or play this miserable licensing key scheme either. It gets even worst when getting into volume licensing for Windows 8 PRO as it will not allow installing the Media Center. We can only do it on a retail version of Windows 8. Well Media Center is an old technology that has its limits and was supposed to work in a workgroup environment only, no PRO version. They rigged it to make it work for PRO rather then really rework it.

I want to give MS the benefit of the doubt and say that they are victim of their own success and have not had a chance to thoroughly work their licensing scheme and it is biting them back you know where. They need to be absolutely clear about their Media Center and not play dumb as they do since they know perfectly well the issue, and it makes them look pretty bad to play this game. A real shame.

For a clean job here is how: http://www.eightforums.com/tutorials/16077-media-center-remove-go-back-windows-8-pro.html

Hope it helps.

April 18th, 2013 12:30am

Hey guys, I am not sure why MS is playing dumb on this one but this is not a bug that needs a fix it. Since the beginning of Media Center, Remote Desktop was only for Admin purposes. Not only that, but the first versions of Windows Media Center would not even allow to register the PC onto a domain. The issue is that they combined the PRO version with the Media Center in their pack upgrade. They should give a choice of upgrading to PRO only, or PRO with Media Center. Actually the Media Center was supposed to be gone on Windows 8, but they kept it because of all the demands.

It basically comes down to reinstalling with a Windows 8 PRO from scratch and not use their PRO pack. It is all a licensing scheme which is really bad. Windows 8 is an awesome evolution that is changing the world of computing. They really do not need to play dumb, or play this miserable licensing key scheme either. It gets even worst when getting into volume licensing for Windows 8 PRO as it will not allow installing the Media Center. We can only do it on a retail version of Windows 8. Well Media Center is an old technology that has its limits and was supposed to work in a workgroup environment only, no PRO version. They rigged it to make it work for PRO rather then really rework it.

I want to give MS the benefit of the doubt and say that they are victim of their own success and have not had a chance to thoroughly work their licensing scheme and it is biting them back you know where. They need to be absolutely clear about their Media Center and not play dumb as they do since they know perfectly well the issue, and it makes them look pretty bad to play this game. A real shame.

For a clean job here is how: http://www.eightforums.com/tutorials/16077-media-center-remove-go-back-windows-8-pro.html

Hope it helps.

KG

I have to disagree with you Karim... this is a bug, and Microsoft needs to fix it.

With or without Media Center, a Pro system should behave as a Pro system. This issue is not limited to Remote Desktop functionality, there are 8 missing builtin security groups that affect other behaviours of Pro too.

Even Microsoft acknowledges it is something to be resolved. This is a quote from a Microsoft support engineer which I received whilst trying to get this issue fixed:

This is a known issue with Windows 8 computer upgraded using Windows 8 Pro Pack. This is an ongoing issue with the Microsoft Global Escalation team and that is currently being worked on. Unfortunately, we dont have or cant provide you a time frame of when this issue will be resolved.

Free Windows Admin Tool Kit Click here and download it now

April 19th, 2013 10:08am

Thanks i74.

This worked perfectly for me and I did not have to switch to using AD. I am using local security and your instructions worked perfectly. Thank you for this fix.

I am disappointed that:

a. Microsoft do not offer full keys to all existing Pro Pack license holders immediately as a workaround.

b. That Microsoft missed this in the first place. How could they not expect that people would only upgrade so they can run Remote Desktop? Maybe they did know but thought they could get away with it? Who knows. If it was deliberate (perhaps they were planning to offer yet another upgrade?) I do know they make enough money and should not do sneaky stuff like this. And if it was not deliberate; how the hell could they not test if remote desktop worked??

Hope they realise people like us waste a lot of time trying to find out why something that should work does not.

i74, you are a whiz. May good more fortune smile on you soon.

Edited by SonicVader Saturday, April 20, 2013 5:12 AM

April 20th, 2013 5:06am

Thanks i74.

This worked perfectly for me and I did not have to switch to using AD. I am using local security and your instructions worked perfectly. Thank you for this fix.

I am disappointed that:

a. Microsoft do not offer full keys to all existing Pro Pack license holders immediately as a workaround.

Hope they realise people like us waste a lot of time trying to find out why something that should work does not.

i74, you are a whiz. May good more fortune smile on you soon.

Edited by SonicVader Saturday, April 20, 2013 5:12 AM

Free Windows Admin Tool Kit Click here and download it now

April 20th, 2013 5:06am

MY DESKTOP REMOTE WON'T WORK EITHER -

OMG its april the 26th 2013 and it looks like I have bough "windows Pro 8 Pro upgrade" , to find out the I can't us "Select Users" to add whilst using Desktop Remote , which is why ,( after Microsoft Sales telling me to buy it ), I bought it . and it does not work !

after much wasted time and reading this very informative page (Great comments btw from all who have written )

I AM TOTALLY amazed that Microsoft tell Customers even 2 weeks ago , that you need to BUY the win8 Pro Upgrade, to get the Remote Desktop access Function, knowing fully well there is a PROBLEM .

THIS Product is not FIT FOR PURPOSE. Is WATCHDOG BACK ON THE TELLY ATM .

CAN ANYONE PLEASDE ADVISE AS OF THE 26TH APRIL 2013 , WHAT THE SITUATION IS - I would be very grateful

THANK YOU , MERCI, DANKE ,TACK

April 26th, 2013 1:06pm

I finally got some time to sit down and research the Remote Desktop issue that has been discussed here. I went through the steps for importing the registery settings into a WIN8 Upgraded to Pro workstation that i74 posted and the registery settings are all there now but I'm still not able to select any users for allowing Remote Desktop because the Select User button is still grayed out. Has anyone received any new information from Micrisoft regarding a fix for this bug?

Thanks

Free Windows Admin Tool Kit Click here and download it now

May 29th, 2013 2:38am

It is definitely a problem with the propack upgrade. Still a problem in June 2013.

June 30th, 2013 12:03pm

I have also experienced this issue.

1)
If you already created the groups manually in Local Users and Groups delete them, as they wont have the correct SIDs like the Builtin groups should.

4)
Repeat step 2 but this time remove your user account from HKLM\SAM\SAM permissions, to restore original permissions.
Restart.

The missing groups are now showing in Local Users and Groups and they are also referenced correctly in the local security policies user rights assignment.

What I do not know is:
- What else could be missed caused by the Pro Pack upgrade routine?
- Are there missing references to the groups somewhere else in Windows?

So I cannot guarantee what future implications there might be, but at least this did solve the immediate issue.

It would be nice if Microsoft could publically acknowledge this issue and provide a Fix-It tool to automate the above and fill in any other gaps that may exist!

i74's fix worked for me but YOU CAN'T ALREADY BE IN A DOMAIN OR IT WON'T WORK.

Since I had already joined the domain, I just did the full reset to default (Settings, PC Settings, General), then i74's regedit hack, then join the domain then add remote users. I also added my user to the administrators local group.

In my case this was a dell PC and had the rather horrible McCrappy AV on it so I had to remove that junk b/f RDP would connect. Good news is now I'm passing domain credentials via RDP to my 'pro upgrade (lols)' PC. Thanks for nothing Microsoft, Thanks a million to i74 - dude you rawk.

Free Windows Admin Tool Kit Click here and download it now

July 3rd, 2013 3:11pm

Hi all - with the July update rollup (KB2855336), there is a fix which resolves the issue with the Pro Pack upgrade scenario. More details on the symptoms in this specific scenario are also documented in KB2850661.

August 5th, 2013 6:00pm

Apologies I have to resurrect this..

I have just upgraded my windows 8.1 to windows 8.1 Pro (x64), primarily to grant rdc permissions to a non-admin and I have exactly this issue. I have just informed Microsoft technical support who have "escalated the issue" even after I showed them the kb articles and patches. I have tried to specifically install the KB2855336 patch but the windows update standalone installer tells me that the patch is not applicable to my computer. So two specific questions: 1) the talk above is for windows 8. The patch was also relevant for windows 8.1 as well ? 2) Given the timescale involved between my purchase and the resolution, shouldn't this be in my core updates anyway ?

Free Windows Admin Tool Kit Click here and download it now

March 30th, 2015 4:54am

Update on this:

I have tried to explain the issue to Microsoft support, pointing them in the direction of this thread and the KBs but was told the issue "had to be escalated" and that I would receive a call back. 3 days later this has not happened, nor have I had any email confirms of our chats. The MS support guy even wanted to show me the websites he was building. What a joke...

April 2nd, 2015 10:57am

I spent 3 hours on the phone with MS support this afternoon. The problem was too advanced for everyone I spoke to so I needed to be forwarded on and on and on and eventually I just got cut off... Its a disgrace.

Free Windows Admin Tool Kit Click here and download it now

April 2nd, 2015 12:55pm

This topic is archived. No further replies will be accepted.